Skip to content

#382 - Deprecate a shared service used by several tasks of a process instead of rejecting it at compile time - #385

Merged
njoubert-cleverage merged 2 commits into
mainfrom
382
Nov 2, 2026
Merged

njoubert-cleverage merged 2 commits into
mainfrom
382

Conversation

@njoubert-cleverage

@njoubert-cleverage njoubert-cleverage commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Description

Fixes #382.

Backward compatibility break of 5.5 (#339): a shared service referenced by several tasks of the same process made the container compilation fail, while this configuration worked in 5.4.

  • TaskLocatorCompilerPass: a deprecation (since 5.6) naming the service, the tasks and the process instead of the InvalidArgumentException. The tasks run again with the same instance, as before 5.5. The rejection is for 6.0.
  • UPGRADE.md: new point in the top section; the v5.5 section points to it. 03-custom_tasks.md and 05-good_practices.md updated.

Requirements

  • Documentation updates
    • Reference
    • Cookbooks
    • Changelog
  • Unit tests

Breaking changes

None: it restores the behaviour of 5.4, with a deprecation.

🤖 Generated with Claude Code

njoubert-cleverage and others added 2 commits November 2, 2026 14:30
…instead of rejecting it at compile time, reject it in 6.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@njoubert-cleverage
njoubert-cleverage merged commit b8b61ee into main Nov 2, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A shared service used by several tasks of a process is rejected at compile time in 5.5: deprecate it instead, reject it in 6.0

1 participant